Cloud and smartphone communication system and method

ABSTRACT

A method, system or apparatus including a server that may receive information from a computer, store the information in a database at the server, determine a reader device to receive the information based on an analysis of a reader device identifier, and transmit viral data to a mobile device where the viral data includes at least a portion of the information.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims the benefit of U.S. Provisional PatentApplication No. 61/684,070 filed on Aug. 16, 2012, the contents of whichare incorporated herein by reference in their entirety.

BACKGROUND

Various devices may be employed for providing information, such asupdated information, to a reader device. Some existing systems havevarious shortcomings relative to certain applications. Accordingly,there remains a need for further contributions in this area oftechnology.

SUMMARY

One embodiment of the present invention is a unique wirelesscommunication system and method. Other embodiments include apparatuses,systems, devices, hardware, methods, and combinations for a wirelesscommunication system. Further embodiments, forms, features, aspects,benefits, and advantages of the present application shall becomeapparent from the description and figures provided herewith.

BRIEF DESCRIPTION OF THE FIGURES

The description herein makes reference to the accompanying figureswherein like reference numerals refer to like parts throughout theseveral views, and wherein:

FIG. 1 is a schematic block diagram of an exemplary system according toone form of the present invention.

FIG. 2 is a schematic block diagram of an exemplary computing device.

FIG. 3 is a schematic flow diagram of an exemplary process forcommunicating with a reader device.

FIG. 4 is a schematic time sequence diagram of an exemplary process forcommunicating with a reader device.

DETAILED DESCRIPTION OF THE ILLUSTRATIVE EMBODIMENTS

For the purposes of promoting an understanding of the principles of theinvention, reference will now be made to the embodiments illustrated inthe drawings and specific language will be used to describe the same. Itwill nevertheless be understood that no limitation on the scope of theinvention is hereby intended. Any alterations and further modificationsin the described embodiments, and any further applications of theprinciples of the invention as described herein are contemplated aswould normally occur to one skilled in the art to which the inventionrelates.

FIG. 1 illustrates an exemplary system 100. In the embodiment shown inFIG. 1, the system 100 is an access control system. However, it iscontemplated that in other embodiments, the system 100 may be directedto a payment system, a transit system, or any other system that utilizesa credential or a unique identifier. The system 100 generally includes aserver or credential management device 102, a mobile device 104, acomputer or computing device 106, and a reader device 108. The server102 may provide a credential management service which, in theillustrated embodiment, includes a cloud application 110. The credentialmanagement service, via the cloud application 110, may generallymaintain a database 111 of access control information, alarminformation, and/or audit history information for various assets. Theserver 102, via cloud application 110, may provide certain servicesrelated to access control, credentials, and other information and/orfunctions related to the reader device 108 such as, for example,statuses, configurations, updates, key management, credentialmanagement, tracking, notifications, etc., as will be discussed ingreater detail below. It is also contemplated that the type of datastored in the database 111 may vary depending on the type of system(e.g., access control system, payment system, transit system, etc.). Itis further contemplated that the server 102 may include multipleservers. Additionally, the server 102 may communicate with the mobiledevice 104 and/or the computer 106 at least partially via the Internet.

In the embodiment shown in FIG. 1, the mobile device 104 is a mobilephone such as, for example, a cell phone or smartphone. However, it iscontemplated that in other embodiments, the mobile device 104 may be atablet computer, a smartcard, or any or any other mobile computing orcommunication device that can store data and communicate with the readerdevice 108. It is also contemplated that the computer 106 may be anytype of computing device such as, for example, a desktop computer, alaptop computer, a tablet computer, a mobile device (e.g., asmartphone), and/or other suitable computing devices know to thoseskilled in the art. In the embodiment shown in FIG. 1, the reader device108 is associated with an electronic lock and is configured tocommunicate with the mobile device 104. However, it is contemplated thatin other embodiments, the reader device 108 may be any other type ofdevice configured to communicate with the mobile device 104 and receiveand/or process credential information or a unique identifier.

In some embodiments, the system 100 utilizes one or more mobile devices104 as a transport or delivery mechanism for delivering information(e.g., access privileges) to the reader device 108 and/or for receivingalarm information and/or audit history feedback from the reader device108. The mobile device 104 may include a Bluetooth transceiverconfigured to communicate with a Bluetooth transceiver that is part ofthe reader device 108. As used herein, the term Bluetooth includesBluetooth Low Energy (BLE). It is contemplated that the mobile device104 and the reader device 108 may communicate via a protocol other thanBluetooth such as, for example, near field communication (NFC) or anyother appropriate communication protocol. The reader device 108 may beintegrated into an electronic lock or be associated with an electroniclock. Other types of suitable reader devices 108 are also contemplatedas would occur to those skilled in the art.

The reader devices 108 (e.g., readers and/or electronic locks) may beincorporated into doors or other access restriction structures ordevices. The reader device 108 may be used to secure a door at aresidential property or a commercial property. The mobile device 104 isconfigured to wirelessly communicate with the cloud application 110 inthe server 102 via an Internet connection, which may utilize, forexample, a cellular data network or other types of wirelesscommunication networks. The mobile device 104 includes a memory forstoring viral data 112 such as, for example, access control information,alarm information, and/or audit histories. The mobile device 104 may beconfigured to transmit feedback data in real-time back to the server 102including the cloud application 110. The mobile device 104 is configuredto implement “viral data” which includes data that does not pertain to aparticular user, but generally pertains to several users. Furthermore,the user is generally unaware that the user is delivering and/orreceiving viral data 112.

Examples of operations that use viral data 112 in the system 100 mayinclude: database updates being sent from the server 102 to the readerdevice 108 via the mobile device 104; door status updates, batterystatus, door audit information, and/or other statuses sent from thereader device 108 to the server 102 via the mobile device 104; a lockconfiguration sent from the server 102 to the reader device 108 via themobile device 104; credentials deleted or created (online or offline)via any node (e.g., mobile device 104 and/or computer 106) in the system100; user tracking implemented by the mobile device 104 sending readerdevice 108 identification (ID) information to the server 102 when themobile device 104 makes a connection with the reader device 108; updatethe data security algorithm or the key management algorithm by sendingthe updated algorithm from the server 102 to the reader device 108 viathe mobile device 104; lock maintenance information may automatically besent from the reader device 108 to the server 102 via the mobile device104; and/or the server 102 may send notifications to one or more mobiledevices 104 such as, for example, “Please close Door X” when the server102 knows Door X is open and a mobile device 104 is in the vicinity ofthe door, or when a door database is out of date, a message may be sentto a mobile device 104 of a system administrator.

The operations that use viral data 112 described above may beimplemented or accomplished with an application 113 on the mobile device104. The application 113 may run in the background of the mobile device104 such that the user of the mobile device 104 may not be aware thatthe application 113 is running. With the application 113 running in thebackground, the mobile device 104 will be able to connect to both theserver 102 and the reader device 108 without the user being aware of theconnection and/or data communications/transfers occurring. When themobile device 104 establishes a connection with the reader device 108,the mobile device 104 may send the ID of the reader device 108 and theID of the mobile device 104 to the server 102. The server 102 mayanalyze the two IDs to determine whether to grant or deny permission forthe mobile device 104 to deliver and/or receive the viral data 112.Accordingly, the server 102 may reply back to the mobile device 104 witha grant/deny message, and/or send any updates as viral data 112 to thereader device 108 using the mobile device 104 as the communicationpipeline.

It is contemplated that updates and/or new information stored at thedatabase 111 at the server 102 may occur dynamically through the mobiledevice 104 without the user of the mobile device 104 performing anyaction. In one embodiment, the mobile device 104 does not have to comein direct contact with the reader device 108 in order for the update totake place. For example, the mobile device 104 may be within a Bluetoothconnection range of the reader device 108, in which case the mobiledevice 104 may deliver viral data 112 to and/or receive viral data 112from the reader device 108 as the mobile device 104 is passing inproximity to the reader device 108.

The computer 106 may be used to create, update, or otherwise modifyaccess information 114 stored at the server 102. Generally, when theserver 102 receives access information 114 from the computer 106 that isto be transmitted to a particular reader device 108, the server 102 (viathe cloud application 110) transmits the access information in the formof viral data 112 to some or all of the mobile devices 104 of users whohave access privileges to the reader device 108 that is to be updated.However, it should be understood that the users do not necessarily haveto have access privileges in order to update the access information. Theserver 102 (via the cloud application 110) may transmit the new orupdated data to only the mobile devices 104 that interact with theparticular reader device 108 most frequently. As another example, theviral data 112 for the reader device 108 may be delivered to each user(i.e., via mobile devices 104) who has immediate access to that readerdevice 108 so that the next user to approach the reader device 108 willdeliver that viral data 112 to the particular reader device 108. It iscontemplated that the viral data 112 may also include firmware updatesand/or activation information for the reader device 108.

In one embodiment, when the viral data 112 is delivered by the mobiledevice 104, the mobile device 104 may report back to the server 102 toverify that the viral data 112 was successfully transferred. Othermobile devices 104 may then be updated by the server 102 to remove thatparticular update (i.e., delete the viral data 112). It is contemplatedthat this viral data updating technique may be used with any number ofdoors and/or reader devices 108.

In some embodiments, the mobile device 104 may receive alarm informationand/or audit histories/trails in the form of viral data 112 from aparticular reader device 108 immediately whenever someone visits thereader device 108 and/or the door. It is contemplated that to ensure theviral data 112 is successfully delivered to the server 102, the viraldata 112 may be transmitted to multiple mobile devices 104 until thereader device 108 receives an update and/or notification that the latestalarm information and/or audit histories/trails were received at theserver 102. Furthermore, it is contemplated that the viral data 112 fromthe reader device 108 may be delivered to the server 102 immediatelyupon receipt. The server 102 may store the received alarms and/or audittrails in the database 111. A user may also utilize the computer 106 toaccess and/or retrieve the alarms and/or audit trails in the database111.

Generally, the memory of the mobile device 104 stores the viral data 112(e.g., access privileges, alarms, and/or audit history data) so that theviral data 112 can be transported from the reader device 108 to theserver 102 via the mobile device 104. Each credential holder (i.e.,mobile device 104) has virtually unlimited memory for viral data 112such as, for example, access privileges, alarm information, audithistory data, firmware updates, and/or any other data to be sharedbetween the server 102 and the reader 108. In one embodiment, the viraldata 112 is transmitted from the reader device 108 to the server 102immediately, which provides near real-time performance.

The use of viral data 112 in the system 100 may provide control ofoff-line reader devices 108 (e.g., electronic locks) and may eliminatethe need to tour the reader devices 108 to provide updates to the readerdevices 108 or gather alarms and/or audit histories from the readerdevices 108.

FIG. 2 is a schematic block diagram of a computing device 200. Thecomputing device 200 is one example of a server, a mobile device, acomputer, and/or a reader device configuration that may be utilized inconnection with the server 102, the mobile device 104, the computer 106,and/or the reader device 108 shown in FIG. 1. The computing device 200includes a processing device 202, an input/output device 204, memory206, and operating logic 208. Furthermore, computing device 200communicates with one or more external devices 210.

The input/output device 204 allows the computing device 200 tocommunicate with the external device 210. For example, the input/outputdevice 204 may be a transceiver, a network adapter, a network card, aninterface, or a communication port (e.g., a USB port, serial port,parallel port, an analog port, a digital port, VGA, DVI, HDMI, FireWire,CAT 5, or any other type of communication port or interface). Theinput/output device 204 may be include hardware, software, and/orfirmware. It is also contemplated that the input/output device 204 mayinclude more than one of these adapters, cards, or ports.

The external device 210 may be any type of device that allows data to beinputted or outputted from the computing device 200. For example, theexternal device 210 may be a mobile device, a reader device, otherelectronic equipment, a handheld computer, a diagnostic tool, acontroller, a computer, a server, a processing system, a printer, adisplay, an alarm, an illuminated indicator such as a status indicator,a keyboard, a mouse, or a touch screen display. Furthermore, it iscontemplated that the external device 210 may be integrated into thecomputing device 200. It is further contemplated that there may be morethan one external device in communication with the computing device 200.

Processing device 202 can be a programmable type, a dedicated hardwiredstate machine, or any combination thereof. The processing device 202 mayfurther include multiple processors, Arithmetic-Logic Units (ALUs),Central Processing Units (CPUs), Digital Signal Processors (DSPs), orthe like. Processing devices 202 with multiple processing units mayutilize distributed, pipelined, and/or parallel processing. Processingdevice 202 may be dedicated to performance of just the operationsdescribed herein or may be utilized in one or more additionalapplications. In the depicted form, processing device 202 is of aprogrammable variety that executes algorithms and processes data inaccordance with operating logic 208, as defined by programminginstructions (such as software or firmware) stored in memory 206.Alternatively or additionally, the operating logic 208 for theprocessing device 202 is at least partially defined by hardwired logicor other hardware. The processing device 202 may include one or morecomponents of any type suitable to process the signals received from theinput/output device 204 or elsewhere, and to provide desired outputsignals. Such components may include digital circuitry, analogcircuitry, or a combination of both.

Memory 206 may be of one or more types, such as a solid-state variety,electromagnetic variety, optical variety, or any combination thereof.Furthermore, memory 206 can be volatile, nonvolatile, or a combinationof these types, and some or all of memory 206 can be of a portablevariety, such as a disk, tape, memory stick, cartridge, or the like.Additionally, memory 206 can store data that is manipulated by theoperating logic 208 of the processing device 202, such as datarepresentative of signals received from and/or sent to input/outputdevice 204 in addition to or in lieu of storing programming instructionsdefining operating logic 208, just to name one example. As shown in FIG.2, memory 206 may be included with the processing device 202 and/orcoupled to the processing device 202.

FIG. 3 illustrates a schematic flow diagram of an exemplary process 300for updating information in a reader device. Operations illustrated forall of the processes in the present application are understood to beexamples only, and operations may be combined/divided and added/removedas well as re-ordered in whole or in part, unless explicitly stated tothe contrary.

Process 300 begins at operation 302 in which a user may use the computer106 to create, update, and/or modify access control information 114 thatis transmitted and/or stored at the server 102. The server 102 may storethe access control information 114 in the database 111.

Process 300 then proceeds from operation 302 to operation 304. Atoperation 304, the server 102, via the cloud application 110, determineswhich reader device 108 should receive new or updated information ordata. The determination may be based on the content of the accesscontrol information 114 that is to be delivered to a reader device 108.For example, the information 114 may include access rights for aparticular reader device 108. It is contemplated that more than onereader device 108 may receive the information 114, for example, insituations where several doors in a building have overlapping useraccess rights.

Process 300 then proceeds from operation 304 to operation 306. Atoperation 306, the server 102, via the cloud application 110, determineswhich mobile devices 104 should be used to virally transfer theinformation 114 from the server 102 to the reader device 108. The server102, via the cloud application 110, may determine the targeted mobiledevices 104 based on the access rights associated with each mobiledevice 104. For example, the server 102, via the cloud application 110,may transmit the information 114 in the form of viral data 112 to someor all of the mobile devices 104 of users who have access privileges tothe reader device 108 (and the associated door) that is to receive theinformation 114. For example, the server 102, via the cloud application110, may transmit the viral data 112 to only the mobile devices 104 thatinteract with the particular reader device 108 most frequently. Asanother example, the viral data 112 for the reader device 108 may bedelivered to each mobile device 104 that has access to the particularreader device 108 immediately so that the next mobile device 104 tointeract with the particular reader device 108 will deliver that viraldata 112 to the reader device 108 as soon as possible.

Process 300 then proceeds from operation 306 to operation 308. Atoperation 308, the server 102, via the cloud application 110, transmitsat least a portion of the information 114 in the form of viral data 112to one or more of the mobile devices 104. The server 102 and the mobiledevices 104 may communicate over an Internet connection. However, it iscontemplated that other communication protocols and/or methods may beused in place of or in addition to the Internet connection.

Process 300 then proceeds from operation 308 to operation 310. Atoperation 310, one of the mobile devices 104 may deliver the viral data112 to the reader device 108. For example, a user of the mobile device104 may be attempting to access a secured room using the Bluetoothand/or NFC transceiver in the mobile device 104. Without the user'sknowledge, the mobile device 104 may transfer a credential and/or otherdata for the access request, but the mobile device 104 will alsotransfer the viral data 112 to the reader device 108. The reader device108 will then store the viral data 112 in the appropriate location inmemory and utilize the viral data 112. As another example, the mobiledevice 104 may be passing by or in the vicinity of the reader device 108in which case the mobile device 104 may connect to the reader device 108without the mobile device 104 attempting to access a secured area.Process 300 then proceeds from operation 310 to operation 312. Atoperation 312, the reader device 108 may send various data to the mobiledevice 104. For example, the reader device 108 may send a confirmationthat the viral data 112 was successfully stored and/or installed in thereader device 108. As another example, the reader device 108 maytransmit alarms and/or audit information to the mobile device 104. It iscontemplated that the reader device 108 may transfer alarm informationand/or audit information in the form of viral data 112 to one or moremobile devices 104 independent of receiving new and/or updatedinformation from the server 102.

Process 300 then proceeds from operation 312 to operation 314. Atoperation 314, the mobile device 104 transfers the viral data 112 thatthe mobile device 104 received from the reader device 108 to the server102. The server 102 and the mobile device 104 may communicate via anInternet connection. If the viral data 112 received from the mobiledevice 104 is a confirmation of a successful update, the server 102, viathe cloud application 110, may notify the computer 106 and/or send acommand to the other mobile devices 104 that also received the viraldata 112 to delete the viral data 112 since the reader device 108 hasalready been updated successfully. If the viral data 112 constitutesalarm information and/or audit histories, the server 102 may store thealarm information and/or audit histories in the database 111.

Process 300 then proceeds from operation 314 to operation 316. Atoperation 316, the computer 106 may download the alarm informationand/or audit histories from the database 111 at the server 102.

FIG. 4 is a schematic time sequence diagram illustrating anotherexemplary process 400 for communicating viral data 112 between theserver 102 and the reader device 108 via the mobile device 104.Operations illustrated for all of the processes in the presentapplication are understood to be examples only, and operations may becombined/divided and added/removed as well as re-ordered in whole or inpart, unless explicitly stated to the contrary.

Process 400 begins with operation 402 in which the reader device 108advertises to one or more mobile devices 104 that the reader device 108is available for communication or connection. The reader device 108 mayadvertise to the mobile devices 104 by transmitting a Bluetooth signalcontinuously or intermittently.

Process 400 then proceeds from operation 402 to operation 404. Atoperation 404, the mobile device 104 responds to the advertisementtransmitted by the reader device 108 by sending one or more responsemessages which in turn initiate and/or establish a connection betweenthe mobile device 104 and the reader device 108 via Bluetoothcommunication, for example.

Process 400 then proceeds from operation 404 to operation 406. Atoperation 406, the reader device 108 may transmit a message thatincludes an encrypted reader device identification (ID) to the mobiledevice 104 via Bluetooth communication. It is contemplated that a uniqueidentifier other than a reader device ID may be transmitted to themobile device 104. Furthermore, it is contemplated that the mobiledevice 104 reader device ID may not necessarily be encrypted when it istransmitted to the mobile device 104.

Next, process 400 proceeds from operation 406 to operation 408. Atoperation 408, the mobile device 104 may transmit a message to theserver 102 that includes the encrypted reader device ID and the mobiledevice ID. The server 102 may decrypt the reader device ID. In addition,the server 102 may analyze the reader device ID and the mobile device IDto determine whether any new or updated information exists for thereader device 108 and/or to verify that the mobile device 104 and thereader device 108 should communicate viral data 112 with one another.

Process 400 proceeds from operation 408 to operation 410. At operation410, the server 102 transmits one or more messages to the mobile device104, which may include new and/or updated information such as, forexample, a user database, time and date, and/or reader configurationupdates. It is contemplated that the information from the server 102 maybe encrypted, and the server 102 and the mobile device 104 maycommunicate via an Internet connection.

Next process 400 proceeds from operation 410 to operation 412. Atoperation 412, the mobile device 104 sends the information from theserver 102 (e.g., an encrypted user database, time and date, and/orreader configuration updates) to the reader device 108 via Bluetoothcommunication. The reader device 108 may then store the receivedinformation and utilize the information in an operation.

Process 400 proceeds from operation 412 to operation 414. At operation414, the reader device 108 transmits a message to the mobile device 104,in which the message may include a confirmation of receipt of theinformation from the server 102. Additionally or alternatively, themessage may also include status information such as, for example, door,battery, audit, and/or maintenance information. It is also contemplatedthat the status information may be encrypted.

Next process 400 proceeds from operation 414 to operation 416. Atoperation 416, the mobile device 104 may send the confirmation and/orstatus message from the reader device 108 to the server 102. The server102 may then process and/or store confirmation and/or the door, battery,audit, and/or maintenance information from the reader device 108 in thedatabase 111 for analysis and/or any other operation.

The various aspects of the process 300 and/or 400 in the presentapplication may be implemented in the operating logic 208 as operationsby software, hardware, artificial intelligence, fuzzy logic, or anycombination thereof, or at least partially performed by a user oroperator. In certain embodiments, operations represent software elementsas a computer program encoded on a computer readable medium, wherein theserver 102, the mobile device 104, the computer 106, and/or the readerdevice 108 performs the described operations when executing the computerprogram.

One aspect of the present application may include a method, comprising:receiving information at a server; storing the information in a databaseat the server; determining a reader device that is to receive theinformation based on an analysis of the information; selecting one ormore mobile devices to deliver the information to the reader device; andtransmitting viral data to the one or more mobile devices, wherein theviral data includes at least a portion of the information.

Features of the aspect of the present application may include:transmitting the viral data to the reader device from one of the mobiledevices; wherein the mobile device and reader device communicate vianear field communication; transmitting audit information from the readerdevice to one of the mobile devices; receiving the audit information atthe server from one of the mobile devices; and storing the auditinformation in the database at the server; downloading at least aportion of the audit information from the database at the server via acomputer; wherein the selecting is based on which mobile devices haveaccess to the reader device; receiving a notification message at theserver from the one mobile device, wherein the notification messageindicates the reader device was successfully updated; and transmitting acommand from the server to all of the other mobile devices to delete theviral data; wherein the information comprises updated access rights forthe reader device; wherein the viral data includes a firmware update forthe reader device.

Another aspect of the present application may include a system,comprising: a server configured to provide a cloud service; one or moremobile devices; and a reader device; and wherein the server isconfigured to: receive information and store the information in adatabase at the server, determine the reader device that is to receivethe information based on an analysis of the information, select one ormore mobile devices to deliver the information to the reader device, andtransmit viral data to the one or more mobile devices, wherein the viraldata includes at least a portion of the information, wherein the mobiledevice is configured to receive the viral data from the server andtransmit the viral data to the reader device; and wherein the readerdevice is configured to receive the viral data from the mobile device.

Features of the aspect of the present application may include: whereinthe one or more mobile devices and the reader device communicate vianear field communication; wherein the system is at least one of anaccess control system, a payment system, and a transit system; whereinthe reader device is further configured to transmit audit information toone of the mobile devices, wherein the server is further configured toreceive the audit information from one of the mobile devices, andwherein the server is further configured to store the audit informationin the database at the server; a computer configured to download atleast a portion of the audit information from the database at theserver.

Yet another aspect of the present application may include an apparatus,comprising: a server configured to receive information, store theinformation in a database at the server, determine a reader device thatis to receive the information based on an analysis of the information,select one or more mobile devices to deliver the information to thereader device, and transmit viral data to the one or more mobiledevices, wherein the viral data includes at least a portion of theinformation.

Features of the aspect of the present application may include: whereinthe server is further configured to: host audit information forretrieval by a computer; wherein the server is further configured to:receive a notification message from one of the mobile devices, whereinthe notification message indicates the reader device was successfullyupdated; and transmit a command to at least one other of the mobiledevices to delete the viral data; wherein the information comprisesupdated access rights for the reader device; wherein the viral dataincludes a firmware update for the reader device; wherein the server isconfigured to select the one or more mobile devices based on whichmobile devices have access to the reader device.

Another aspect of the present application may include method,comprising: transmitting a reader device identifier from a reader deviceto a mobile device via a wireless connection; receiving the readerdevice identifier at a server from the mobile device; determining viathe server updated information for the reader device to receive based onan analysis of the reader device identifier, wherein the updatedinformation is stored in a database at the server; and transmittingviral data to the mobile device, wherein the viral data includes atleast a portion of the updated information.

Features of the aspect of the present application may include:transmitting the viral data to the reader device from the mobile device,wherein the viral data is transmitted to the reader device in abackground operation of the mobile device; wherein the wirelessconnection is a Bluetooth connection; transmitting status informationfrom the reader device to the mobile device; receiving the statusinformation at the server from the mobile device; and storing the statusinformation in the database at the server; downloading at least aportion of the audit information from the database at the server via acomputer; advertising via the reader device to establish a connectionwith the mobile device via Bluetooth communication; receiving a mobiledevice identifier at the server from the mobile device; and analyzingthe mobile device identifier and the reader device to determine whetherto use the mobile device to communicate viral data to the reader device;wherein the information comprises a user database for the reader device;wherein the viral data includes a firmware update for the reader device.

Yet another aspect of the present application may include a system,comprising: a server configured to provide a cloud service; a mobiledevice; a reader device; and wherein the server is configured to:receive a reader device identifier from the mobile device; determineupdated information for the reader device to receive based on ananalysis of a reader device identifier, wherein the updated informationis stored in a database at the server; and transmit viral data to themobile device, wherein the viral data includes at least a portion of theupdated information, wherein the mobile device is configured to receivethe viral data from the server and transmit the viral data to the readerdevice; and wherein the reader device is configured to receive the viraldata from the mobile device.

Features of the aspect of the present application may include: whereinthe mobile device and the reader device communicate via Bluetooth;wherein the system is at least one of an access control system, apayment system, and a transit system; wherein the reader device isfurther configured to transmit status information to the mobile device,wherein the server is further configured to receive the statusinformation from the mobile device, and wherein the server is furtherconfigured to store the status information in the database at theserver; a computer configured to download at least a portion of thestatus information from the database at the server.

Another aspect of the present application may include an apparatus,comprising: a server configured to receive information, store theinformation in a database at the server, determine whether to transmitat least a portion of the information to a mobile device based on ananalysis of a reader device identifier and a mobile device identifier,and transmit viral data to the mobile device, wherein the viral dataincludes at least a portion of the information.

Features of the aspect of the present application may include: whereinthe server is further configured to: receive status information from themobile device, wherein the status information includes data related tooperation of the reader device; wherein the server is further configuredto: host the status information for retrieval by a computer; wherein theinformation comprises a user database for the reader device; wherein theviral data includes a firmware update for the reader device; whereinserver is configured to communicate with an application on the mobiledevice that operates as a background operation on the mobile device.

While the invention has been illustrated and described in detail in thedrawings and foregoing description, the same is to be considered asillustrative and not restrictive in character, it being understood thatonly the preferred embodiments have been shown and described and thatall changes and modifications that come within the spirit of theinventions are desired to be protected.

It should be understood that while the use of words such as preferable,preferably, preferred or more preferred utilized in the descriptionabove indicate that the feature so described may be more desirable, itnonetheless may not be necessary and embodiments lacking the same may becontemplated as within the scope of the invention, the scope beingdefined by the claims that follow. In reading the claims, it is intendedthat when words such as “a,” “an,” “at least one,” or “at least oneportion” are used there is no intention to limit the claim to only oneitem unless specifically stated to the contrary in the claim. When thelanguage “at least a portion” and/or “a portion” is used the item caninclude a portion and/or the entire item unless specifically stated tothe contrary.

What is claimed is:
 1. A method, comprising: transmitting a readerdevice identifier from a reader device to a mobile device via a wirelessconnection; receiving the reader device identifier at a server from themobile device; determining via the server updated information for thereader device to receive based on an analysis of the reader deviceidentifier, wherein the updated information is stored in a database atthe server; and transmitting viral data to the mobile device, whereinthe viral data includes at least a portion of the updated information.2. The method of claim 1, further comprising: transmitting the viraldata to the reader device from the mobile device, wherein the viral datais transmitted to the reader device in a background operation of themobile device.
 3. The method of claim 1, wherein the wireless connectionis a Bluetooth connection.
 4. The method of claim 1, further comprising:transmitting status information from the reader device to the mobiledevice; receiving the status information at the server from the mobiledevice; and storing the status information in the database at theserver.
 5. The method of claim 4, further comprising: downloading atleast a portion of the audit information from the database at the servervia a computer.
 6. The method of claim 1, further comprising:advertising via the reader device to establish a connection with themobile device via Bluetooth communication.
 7. The method of claim 1,further comprising: receiving a mobile device identifier at the serverfrom the mobile device; and analyzing the mobile device identifier andthe reader device to determine whether to use the mobile device tocommunicate viral data to the reader device.
 8. The method of claim 1,wherein the information comprises a user database for the reader device.9. The method of claim 1, wherein the viral data includes a firmwareupdate for the reader device.
 10. A system, comprising: a serverconfigured to provide a cloud service; a mobile device; a reader device;and wherein the server is configured to: receive a reader deviceidentifier from the mobile device; determine updated information for thereader device to receive based on an analysis of a reader deviceidentifier, wherein the updated information is stored in a database atthe server; and transmit viral data to the mobile device, wherein theviral data includes at least a portion of the updated information,wherein the mobile device is configured to receive the viral data fromthe server and transmit the viral data to the reader device; and whereinthe reader device is configured to receive the viral data from themobile device.
 11. The system of claim 10, wherein the mobile device andthe reader device communicate via Bluetooth.
 12. The system of claim 10,wherein the system is at least one of an access control system, apayment system, and a transit system.
 13. The system of claim 10,wherein the reader device is further configured to transmit statusinformation to the mobile device, wherein the server is furtherconfigured to receive the status information from the mobile device, andwherein the server is further configured to store the status informationin the database at the server.
 14. The system of claim 13, furthercomprising: a computer configured to download at least a portion of thestatus information from the database at the server.
 15. An apparatus,comprising: a server configured to receive information, store theinformation in a database at the server, determine whether to transmitat least a portion of the information to a mobile device based on ananalysis of a reader device identifier and a mobile device identifier,and transmit viral data to the mobile device, wherein the viral dataincludes at least a portion of the information.
 16. The apparatus ofclaim 15, wherein the server is further configured to: receive statusinformation from the mobile device, wherein the status informationincludes data related to operation of the reader device.
 17. Theapparatus of claim 16, wherein the server is further configured to: hostthe status information for retrieval by a computer.
 18. The apparatus ofclaim 15, wherein the information comprises a user database for thereader device.
 19. The apparatus of claim 15, wherein the viral dataincludes a firmware update for the reader device.
 20. The apparatus ofclaim 15, wherein server is configured to communicate with anapplication on the mobile device that operates as a background operationon the mobile device.